-
Notifications
You must be signed in to change notification settings - Fork 907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Omnibar position option #4885
Omnibar position option #4885
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
99ecf5e
to
adaf626
Compare
adaf626
to
e6f425a
Compare
efd808b
to
dcd1d5e
Compare
ed0ac91
to
b906747
Compare
1ab54e1
to
2b7eaca
Compare
40ecd9e
to
b0dd837
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a couple of outstanding comments from previous PR.
The big issue is that when the omnibar is at the bottom we are over the web content, and not properly pushing it to the top. That makes it so any content at the bottom of the viewport is behind the omnibar.
app/src/main/java/com/duckduckgo/app/browser/BrowserTabFragment.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/com/duckduckgo/app/browser/BrowserTabFragment.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/com/duckduckgo/app/browser/BrowserTabFragment.kt
Outdated
Show resolved
Hide resolved
* limitations under the License. | ||
*/ | ||
|
||
package com.duckduckgo.app.browser.omnibar.model |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this in the browser-api module?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on what I observed, it seemed like the right place to put a common model that might be accessed by different modules in the future. If you feel it’s not the right place I’m open to suggestions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If another module would need to access the omnibar position, they will do it via the SettingsDataStore
. You have placed the model in the browser-api
module, but the public accessor to that value is in the app module.
This module is specifically for things related to the browser. The omnibar and it’s position are separate from that. In other words, omnibar doesn’t need to know anything about the browser. I’d move it to the same app/omnibar package you have the rest of the logic.
7bd0bd1
to
cd4a537
Compare
@malmstein Thanks for the review. I will fix this in a separate PR. The rest of the comments should be addressed now. I added steps for testing different scenarios in the PR description. |
1672676
to
37114ff
Compare
This stack of pull requests is managed by Graphite. Learn more about stacking. |
37114ff
to
3864a65
Compare
…visible scrollable
d0678eb
to
0175a60
Compare
@malmstein I’ve updated the test instructions to include tests of the feature flag, as well. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good and works as expected. Thanks @0nko !
Task/Issue URL: https://app.asana.com/0/1207418217763355/1208356719296150/f
Description
This is a feature branch for the omnibar position project.
Testing instructions
Dummy toolbar
Autocomplete
UI changes
Snackbar
This patch will triggers a snackbar after tapping the fire button:
UI changes
Privacy pop-up dialog
UI changes
Onboarding messages
UI changes
Feature flag tests
Bottom bar enabled
Use
https://www.jsonblob.com/api/1287776240176848896
privacy config URL and theplayRelease
build, so that the feature flag is enabledAddress bar
option to change the omnibar positionBottom bar disabled
Use
http://www.jsonblob.com/api/1287777925473361920
privacy config URL, so that the feature flag is enabledAddress bar
option is not visible